I think we're making some progress.
Let's start with the simple thing: the "memory leak" in the dynamic calling example. You allocate a new instance of the reentrant dynamic VI on every loop iteration, although you only run it when the button is pushed. That leaves you with huge numbers of allocated, idle instances of the VI, and eventually you run out of memory. The solution is obvious - move open VI reference into the case structure. Close Reference should go into the case structure too.
That said, I suspect that your original issue, if it exists, can be solved without dynamically calling any VIs. If you can provide code that demonstrates a specific problem, or if you can provide a better (simpler?) explanation of the problem, then I can try to help with a solution.
Considering rewriting the code shown in the Untitled2.png screenshot to use a more standard producer-consumer pattern with a single event structure in its own loop at the top level. It's not a good idea to put event structures inside case structures, as has been explained in multiple threads in this forum.
