If one happens to have a service that is configured to be lazy AND also implementsResetInterface, when Symfony resets resettableService, it will callreset on the service which will trigger the initialization even though the service has not been actually used by the code, which defeats the purpose of having the service lazy.
To fix this I propose to skip resetting a service that is marked asLazyObjectInterface and has not been initialized (ie not used yet)