When a bad EJB is deployed and then looked up remotely, a NPE is thrown - see attached stack trace.

Steps to reproduce:
1) Start AS 5 and deploy the attached EJB - ejb-stateful-1.0-SNAPSHOT.jar .
2) Run the client - EjbClient-1.0-SNAPSHOT.jar , class ejbtest.EjbClient.StatefulClient
This has quite many dependencies, so it's good idea to open the mvn project (in the attached zip) and use some IDE's "Run file" function.

Upon ctx.lookup(), the NPE occurs.

----------------

The EJB has:

public interface Counter { }

@Remote
public interface CounterRemote extends Counter { }

@Stateful
@Remote(CounterBean.class)
public class CounterBean implements Counter { }

-------

The client jar contains (incomplete list):

public interface Counter { }

@Stateful
public class CounterBean implements Counter { }

(this wild combination arose when testing