This error is unexpected.
Take a look at the JBoss AOP jars and check whether they are placed correctly. If they are, I think reinstalling JBoss AOP in the new server (an instalation script is included in the release) is worth a shot.
Reply to this message by going to Community
Start a new discussion in JBoss AOP at Community