The following is not critical, but
When SchedulingConfig is scanned only for the RootApplicationContext (and known that the ServletApplicationContext must be able to use/access the RootApplicationContext beans) my @Components working with @Schedule in the ServletApplicationContext does not work.
The current solution is scan SchedulingConfig from the ServletApplicationContext
Thus seems mandatory scans twice this SchedulingConfig from the RootApplicationContext (consider a batch process where web is not involved) and ServletApplicationContext (consider Websocket, sending messages to a JMS destination, working SimpMessagingTemplate )
It is similar than (prior when to be fixed of course):
I am assuming this situation would be the same or reflected for a @Configuration class working with @EnableAsync