Is it expected that the container validates these dependencies and fails deployment if they don't exist? I think it is, right? At least, I think some containers behave this way. Then we should say that this validation should not happen if the annotation appears in a class annotated @Alternative. I have no idea what the right language would be...