You can also just right click on the module and choose restart.
Currently we've decided to not force a restart on .class changes because of two things:
1) when you use debugging you would no longer benefit from JDT/Java's hotcode replace when just changing the body of a class.
2) if we restart modules on every .class save you sessions will get lost. (This one was a bigger problem in previous AS's because of slower restarts)
...but just these 2 last weeks we got so many people saying this exact feature request so we will look into it - but I would love to hear if (especially #1) doesn't bother you during tomcat/glassfish usage ?