I am also interested in a solution to this besides using @PersistenceContext.
If your EJB executes locally, then I guess the manual lookup Component.getInstance(
em) should work - just place it in your getEm() as a fallback to when em is null.
Not a bad idea, I should give this a try and see how it goes.
Reviving this thread. I don't know what I was thinking when I first replied. I'm not reusing the stateless services in a local context but a remote context where no Seam conversation or Seam session is available, therefore bye bye SMPC.
Anyone got a way to solve this problem without injecting both @In entityManager and @PersistenceContext entityManager to my stateless service EJB?