Using a WeakReference to remember LUA script cache looks like a cause of server script memory exhaustion?

This is a kind of half-finished psychic-debugging style investigation so take my theory with a grain of salt but...
I investigated a redis server crash where the LUA script space was exhausted, and found my way to the pages on LUA scripting with SE.redis (the library being used)

https://stackexchange.github.io/StackExchange.Redis/Scripting.html

and the source for LoadedLuaScript, which is stored with a weak reference.

In this scenario they keep using (reusing) a single LUA script, but they still eventually exhausted the server LUA scripting memory.

I hear (TBV) that they are calling ScriptEvaluate and it eventually becomes EVALSHA under the hood.

This would involve calling Prepare, which seems to use WeakReference for caching under the hood.

https://github.com/StackExchange/StackExchange.Redis/blob/ae6419a164600b4b54dd7ce8a699efe8e98d8f1c/src/StackExchange.Redis/LuaScript.cs#L91

Unfortunately, I think the problem in practice with storing loaded lua scripts with a weak reference is that those weak references WILL get garbage collected and so the prepared cached script is forgotten by the client -- leading to eventually reloading the LUA script in the server unnecessarily, right?

A possible solution here might be using something 'smarter' or 'more robust' than WeakReference to solve this same problem. For instance, I don't know, MemoryCache?

Start with src/StackExchange.Redis/LuaScript.cs around line 91 and read the Scripting documentation linked in the issue. Verify whether Prepare's WeakReference can be collected while the same Lua script is reused, and whether that leads to repeated server-side loading. Done means confirming or disproving the suspected cache behavior and identifying a robust caching approach if the behavior is confirmed.