as the changes happen on distinct requests to a specific end point, i think the global flush is good enough. if you would happen to have some listener hooked into the request that tinkers with managed objects but does not want that to be stored, you just will have to avoid that this triggers for this route.

i can see the much more likely case that you have something like https://github.com/symfony-cmf/RoutingAutoBundle and actually want additional objects you create to be flushed.