1.Lifecycle Management : Individual enterprise beans do not accept to explicitly manage process allocation, object activation, thread management, or object destruction. The EJB container automatically accepts the object lifecycle on behalf of the enterprise bean.

2. State Management : Individual enterprise beans do not use to explicitly restore or save conversational object state between function calls. The EJB container automatically provides object state on behalf of the enterprise bean.

3. Security : Individual enterprise beans do not have to explicitly authenticate users or check authorization levels. The EJB container automatically gives all security checking on behalf of the enterprise bean.

4. Transactions : Individual enterprise beans do not accept to explicitly specify transaction demarcation code to participate in distributed transactions. The EJB container may automatically manage the start, commitment, enrolment, and rollback of transactions on behalf of the enterprise bean.

5. Persistence : Individual enterprise beans do not need to explicitly store or retrieve persistent object data from a database. The EJB container may automatically provide persistent data on behalf of the enterprise bean.