EM dependencies resolution sometime exclude less transitive dependencies than Maven

The use case is the following:

• project
  • dependency1 (excludes dependencyC)
    • dependencyA
      • dependencyC
  • dependency2
    • dependencyB
      • dependencyC

In the case of Maven you don't get dependencyC at the end, while in the case of EM you do: the reason is that since Maven handled dependencyC once already, it does not try again.

It does not seem fully correct to me, but I don't know if it's been done like this on purpose (i.e. we can count on it to be maintained in the future, and we should try to replicate it) or if it's just an unforeseen side effect of what was only supposed to be an optimization.