What Max is saying is that restarting the module every single time you save a changed class file is too much overhead and will slow you down. It is not a good suggested use-case to restart the module after every single publish.
There is currently no way for standard EJBs to hot-swap changed class files, and so you're right in that a full publish is needed... but the user should be required to do that himself, because if after every single 'save' the module was restarted, it could slow down your development substantially.
Of course I can see your argument to the contrary, if every time you wanted to reload the classes you had to by-hand go 'full publish' the module. However as of now, this is not possible. Sorry.