Interesting. I have an @AroundInvoke public Object logTiming InvocationContext ctx) in the base class of my stateless session beans and it is executed during SeamTests as well. I can see the messages being printed during integration tests.
Perhaps because I don't use a separate interceptor class in this case. Can you reproduce your problem with this approach?
Thanks for the idea.
I got the same result...