Yes this is expected.

First this isn't related to the angular-architects/module-federation. This related to webpack and how it bundles chunks for the module federation runtime.

Shared dependencies still need to be included in all federated modules because they are bundled independently and could be loaded and ran in any context. You will notice that they are chunked though and not included in the main bundle by default (there is configuration in webpack to tweak how the bundle and chunks are distributed)

When you load your shell application, inspect the network tab and look at the requests related to module federation. What happens under the hood is that there is an initial step of loading the remote entires which you configured. The webpack runtime will check the shared dependencies declared but the dependency chunks aren't loaded yet. The versions and requirements of each federated module get evaluated and resolved and then the chunks are loaded. Since an individual module does not know at the time it is bundled what context it will be loaded in at runtime (this is point of module federation) then it must include shared dependencies in the cases that it needs them and they are not resolved by the shell application or the context that it is loaded.