So to answer my own question:
The problem is better known as
self invocation. The behavior is expected (well, kind of), more details in discussions linked by:
One cannot change this behavior without providing another, subclass-based aop solution (actually it is quite easy to integrate custom solution with CDI, as one can transform class before the bean is build with help of portable extensions).