1) was already fixed in CVS.
2) um, not certain that there is much I can do about that, but what is the stack trace?
3) I guess this is a limitation of EJB3 packaging, entities probably need to be directly inside the .ejb3 or they wont be found when EJB3 or Seam scan the archive
