Resource scanner does not scan REST resources on multiple interfaces for single implementation

We have some requirement on top down REST api design approach - api designer is able to generate interfaces from spec (OAS) and there may be multiple versions of the spec implemented simultaneously (preserving backwards compatibility for api consumers). As a result, rs endpoint definition ends up with multiple java interfaces containing resources annotated with @Path.

For the deduplication reason, single implementing class is desired and looking into RestEasy scanner (resteasy 3.6.1, wildfly 14 ) - it only register one interface (first it finds during startup path registration). Classes in question are:

https://github.com/resteasy/Resteasy/blob/3.6/resteasy-jaxrs/src/main/java/org/jboss/resteasy/core/ResourceMethodRegistry.java
https://github.com/resteasy/Resteasy/blob/3.6/resteasy-jaxrs/src/main/java/org/jboss/resteasy/util/GetRestful.java

Is this scanner behavior intentional for some reason or considered a bug?