You'll get an error at startup. That's the whole point of Web Beans. It is deterministic.
aha, so similar to what happens in a Seam app when you have more than one Seam component annotated with @Name("foo")
Yep. You can get some overlapping by using deployment types but even then there is an enabled order in configuration.
everything is a Beandoes have some implications in inheritance when you have a class Foo that extends Bar that extends Tar and inject for API type Tar and get hit with ambiguous resolves.