Is there a workaround for this? It looks like Seam-Injection depends on a JNDI name. The EJB 3.0 spec does not require local EJBs ro have one and WebLogic 11 doesn't create on by default. This means that local EJBs are not accessible to Seam when deployed in a WebLogic environment.
We also tried assigning a global JNDI name via the @Stateless(mappedName) property but no entry was added in the global/local JNDI tree. It seems that Weblogic also ignores it as the spec says it is optional http://java.sun.com/javaee/5/docs/api/javax/ejb/Stateless.html#mappedName%28%29
As far as I can see this means that to have a reasonably consistent approach I have to make all EJBs remote and take the performance hit.