This error you are seeing is totally unexpected, as this feature is part of our testsuite.
What is the version of JBoss AOP you are using? (you can check on the manifest of jboss-aop.jar in the server)
Have you tried this scenario on JBoss AOP standalone?