on the one hand, that line of thinking is the next logical step as we moved the classes to the pvm.jar
but making the pvm.jar deployable as an enterprise jar is not good i think.
i would prefer it we kept the separate ejb deployment files in a separate pvm-enterprise.jar
i don't mind if building that jar is part of the pvm project, though.
mostly gutt-feeling instincts speaking. i haven't yet analysed all the arguments in depth...