Can it be important to call remove() on an EJB 3 stateless session bean? Perhaps on weblogic?

I'm not familiar with WebLogic's implementation, but I can't imagine that it's important. I expect each method invocation on an SLSB wrapper to allocate a bean from the pool before the method invocation and free it after, so there is nothing for remove() to do.

I'm not familiar with WebLogic's implementation, but I can't imagine that it's important. I expect each method invocation on an SLSB wrapper to allocate a bean from the pool before the method invocation and free it after, so there is nothing for remove() to do. I would write it off as cargo-cult programming.As a guess, someone once forgot to call remove for an SFSB and found that bad things happened, so the pattern was extended to all session beans.

That's right. You don't implement EJBObject in EJB 3 that's why you cannot call the remove() method. What actually the EJB 3 has, is the dependency injection, which works with the EntityManager.

Nowadays, I am migrating the applications from EJB 2.1 to EJB 3 and I have recognized that I could solve this problem via EntityManager @Resource private EntityManager em; and in a remove method you can write em. Remove(yourObject); Hope this helps.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.