As reported here, it seems that under certain circumstances, the BeanFactory expects ContextAnnotationAutowireCandidateResolvers to expose a default constructor which limits the ability to populate instances with configuration on construction.
Comment From: jhoeller
This is coming from DefaultListableBeanFactory.copyConfigurationFrom for the special purpose of building internal copies of a given BeanFactory in certain scenarios. Replacing its AutowireCandidateResolver handling with a Cloneable arrangement instead of a hard BeanUtils.instantiateClass call seems to be a straightfoward and flexible enough solution here.