EAR deployments are creating unnecessary and wrong EJB ModuleDeployment services

This is being installed using archive name as both the app and module name, if there is an archive in the deployment with a similar name then this can race with the service for that module, and if the EAR's module ends up being the last one to start then the EJB's will not be available.

This is causing intermittent failures in NestedRemoteContextTestCase