WAS 7 supports JEE 5, so, there is no support for beans.xml (which is anyway CDI and not related to EJB).
And, I don't see either a @Local or @Remote declaration on the EJB interface.
SCJP 1.4, OCMJEA/SCEA 5.0.
Joined: Jun 11, 2009
Now the ejb3.0 is working. The solution was to change my maven project type to the "ejb" and use the ejb 3.0 version in the maven ejb plugin.
Yes, you are correct the beans.xml is not needed.
But the @Local annotation is not needed. I checked from the EJB3.0 specification:
ejb-3_0-fr-spec-simplified.pdf page 16
If bean class implements a single interface, that interface is assumed to be the business interface
of the bean. This business interface will be a local interface unless the interface is designated
as a remote business interface by use of the Remote annotation on the bean class or
interface or by means of the deployment descriptor.