This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
I am not sure if I understand your question correctly.
What I can say is that the EJB container only makes sure that a bean instance is associated with only one thread at a time.
A static field can still be accessible across all threads. So thread A (associated with EJB instance A) can start a transaction and access and modify the static field. Simultaneously thread B (associated with EJB instance B) can start another transaction and access and modify the same static field at the same time.
May not understand your question properly, why someone wants to use a Static variable in Ejb ? You want have that in Stateless bean ? What is the purpose , One of the very important features that EJB-Container
provided is Thread-safety. So if you use Static in your EJBs, those are not Thread Safe.
One more thing, if you are looking for having some Singleton Classes in EJB layer, you can have that with latest EJB 3.1
The following bean load data in init() method and saves the data when destroyed