Following up on #21843 in 6.1.3, it turns out that this commonly causes performance regressions, unnecessarily introspecting non-annotated methods in complex class hierarchies on startup. Revisiting the algorithm in BridgeMethodResolver#findBridgedMethod and its use in AutowiredAnnotationBeanPostProcessor and co, these performance regressions should be remedied as of 6.2.13, with introspection performance even having improved over pre-6.1.3 now.