Andrei Stefan opened SPR-6123 and commented
A large number of ShadowMatchImpls objects are created and cached in case a simple execution() pointcut is used. In case this pointcut is combined with a within() clause, as pointed out here: http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg10969.html, the problem goes away, since the method matching in beans is stricter.
It would be good to reflect this advice in the Spring documentation, as well.
Affects: 2.0.8, 2.5.6, 3.0 M4
Referenced from: commits 10e26e6