I believe it is. I have indeed the same problem with interceptors in one of my other tests. Atm, the only part that I can use in war-file embedded in an ear-file is @Inject/@Produces/@Observers.
Whenever I use @Instance I am limited to what is in that one war/jar/... finding something in an external jar fails
Whenever I use something that needs configuration in beans.xml it blows up in my face.
I lost some time developing something in a standalone web project and then finding out that other rules apply when using the same code in an enterprise project.
In an earfile, CDI is nothing more that an advanced replacement for JSF @ManagedBean and @ManagedProperty.
I doesn't make me mad as much as it makes me sad to see so much potential go unused. :(
I hope that my reply on your other thread might cheer you up a bit. In fact, when you take into account the visibility rules, CDI in an earfile is just as powerful as it is in the context of a war deployment. Or at least it will be as soon as that JIRA issue is solved. Suggestion: vote for it :-).