I don't think this needs to be clarified. Stereotypes are clearly defined to be used to "declare some common metadata for beans", ie. are only considered when declared on a bean class or a producer. The spec cannot cover all the possible combinations of incorrect annotations. If we check stereotypes, then why not for example qualifiers, scopes, etc.?

So -1 for throwing a definition exception. We could possibly log a warning but I'm not sure about the additional value.