The EJB container is responsible for instantiating session EJB and removing them when the application starts and eventually is destroyed.
The lifecycle for a stateless session EJB is fairly straightforward. We really can think of them as poolable beans, that is, components that are instantiated by the EJB container from collection of EJB instances. A system administrator can configure the size of the preallocation of each type of EJB in an application.
This is completely an anathema to the current cloud provider configuration. Read more at cloud providers, auto scaling, and roles in Online Chapter, Moving Java EE.next to the Cloud.
A stateless session EJB has two states. The first state ...