interfaces cannot be used to define persistence...
BTW, mocks are unnecessary in EJB3, especially with JBoss Embedabble EJB 3.0.
Makes sense from a persistence perspective... So, EJB3 doesn't support an interface-based programming model for entity beans. I guess I was taking this concept of programming using POJOs too literally. Also, I'll have to consider using embedabble EJB 3.0 for my testing strategy.