The EJB3 subsystem starts many services to provide EJB-related functionality:

• basic services like DeploymentRepositoryService and AssociationService which are used to process EJB-related invocations, whether local or remote
• remote connector services, used only when invocations are received from outside the server via the EJB client
• clustering-related services, when deployments appear in the context of a HA server configuration
• IIOP-related services
• and other such services

At present, many services in the ejb3 subsystem are started whether they are needed or not, and this leads to unnecessary use of the server's existing memory and processing resources. A better option is to only start services when they are needed.

This issue concerns going through the set of services provided by the ejb3 subsystem and moving their start mode from ACTIVE/LAZY/PASSIVE to ON_DEMAND wherever possible, and setting up any additional dependencies required to make this work, so that services are only started as and when needed.