I found an old issue related to this: https://issues.jboss.org/browse/EJBTHREE-466
I wonder why a simple issue is not fixed for so many years. No annotation can be used without this fix. JBOSS may as well remove the feature if there are not willing to fix.
Can you post a relevant example where this is causing problem?
Well issue you linked has no relation to WildFly / JBoss AS7+ whatsoever.
That jira project was for tracking implementation of EJB3 in older versions of application server and also as standalone project.
Claiming this is an issue based on unrelated bug report is bit silly.
AnnotationValue/AnnotationInstance objects you are referring to are internal Jandex API that WildFly uses for indexing annotations.
This is never exposed to deployment itself, think of it as implementation detail on how we can process annotations in deployment in performant way.
To learn more about jandex look at GitHub - wildfly/jandex: Java Annotation Indexer