When @target is used in a PointCut, all beans created in the same context are proxied, although that PointCut does not match those beans.
This bug was already mentioned and according to that ticket also fixed (https://jira.spring.io/browse/SPR-2168), but this behavior is still present in later versions of Spring.
In our application context some beans cannot be proxied. These beans cannot be modified, so usage of @target PointCuts breaks our application. However, not using @target is also not possible, as our use case requires Aspects to be applied to all methods of a wide range of classes (including inherited and interface methods). Our desired behavior for aspects could not be implemented with other PointCut definitions.