I don't know, sorry.

OK, let's go withdoctrine/DoctrineBundle#1528 for now

To me, the best solution for that would be to implementEntityManager::reset, that would recreate a UnitOfWork and reopen the EntityManager, instead of having to replace the EntityManager instance itself. This way, an EntityManager could be reset safely in a long running process like a queue consumer, even in case an exception happens when handling one message.
This would remove the need to use a proxy for the EntityManager (which was just a hacky way of making the EntityManager compatible with such use case).

What this mean@stof is that we cannot implement#35345 until ORM figured out a proper way to reset its state. Did I get you correctly?

I updated the PR to throw instead of ignoring. This shouldn't happen in practice since we don't generate ghost object proxies, but let's merge as a defensive measure.

Thank you@nicolas-grekas.