Going by your words above there still are some classes in our application that are coupled to the Container (or service locater). The way I understand this., every thing up to our services/controllers can be auto wired by the Container. But then all the clients (as in code/classes) using our controllers and services need to be coupled to the container to request these service and controller instances.
Is my understanding right? Which would mean all our tests for the clients using these services and controllers would need to manage the container dependency. Is this correct? Or is there a way to work around this dependency too.
Can you be a bit more specific in highlighting what are the classes you see that would be coupled to the container (or service locater).. what roles or responsibilities would they have?