After Symfony Kernel reboot - Doctrine EventManager keep old Container

#### What are you trying to achieve?
I have case, when my service have some state, like MemoryStorage collect some data and I want to test what it collects. This MemoryStorage filled by some listeners, subscribed to Doctrine events.

#### What do you get instead?
My MemoryStorage empty.

Here is reproduce test https://github.com/ewgRa/symfony-standard/blob/codeception-bug-with-container/tests/functional/ContainerCest.php .

tryToTest failed, and tryToTestProof show the reason why it fail.
Problem that doctrine.orm.entity_manager is persistent service and it have EventManager, that actually ContainerAwareEventManager, that store container.
When Symfony module reboot kernel, it create new Container, but since doctrine is persistent, EventManager continue keep old container.
As a result Doctrine events work with its own container, while $I->grabService(...) work with another container.

Reproduce:
git clone git@github.com:ewgRa/symfony-standard.git
cd symfony-standard/
git checkout codeception-bug-with-container
composer install
vendor/bin/codecept run

So, is it feature? Or bug? Looks like 100% bug. Possible solution is update EventManager container also on kernel reboot. Or another solution - unpersist doctrine.

At least this must be mentioned somehow in documentation. Also some "I make service persistent, and it not works" issues can be related to this.

Run the reproduction from tests/functional/ContainerCest.php using the documented git checkout, composer install, and vendor/bin/codecept run commands. Inspect the Symfony kernel reboot path, doctrine.orm.entity_manager persistence, and ContainerAwareEventManager to confirm why the old container remains referenced. Done means a regression test demonstrates consistent container use, or the limitation is documented if no fix is selected.

Vom Indexierungsmodell aus dem Issue-Text verfasst.