Beans proxied by the Spring container with declared CQs are not registered and triggered

When beans declared in the Spring container are proxied (to apply and "decorate" those beans with additional capabilities, e.g. Caching, Security or Transaction Management, basically any "cross-cutting" concern where an AOP Proxy is applied), then a CQ annotated callback service method is not identified properly, and subsequently, the CQ is never registered and triggered accordingly.