Enterprise application architecture for boundary testing

I have a big Java EE (jee6/jdk7) application deployed on an application server, which depends on a lot of other applications deployed on the same server. They all publish interfaces which I use via remote EJB. For each service, there is an module inside of my application which acts as an adapter.

When I perform e2e/integration testing I want to use mocks instead of real services, but I also want to decide whether to use mocks or real services on runtime (with robot framework) - not compile time and to have production code preferably no information about mocks.

Any ideas on what patterns to use? Service stub presented in PEAA provides too much knowledge about tests to production environment