Interceptors spec, 2.2.1 - Interceptor Environment:

Interceptor class shares the enterprise naming context of its associated target class. (1)

Assume the following scenario:
Ear: test-ejb.jar, test1.war, test2.war
test-ejb.jar: Animal, BarBinding
test1.war: BarInterceptor, Dog
test2.war: Bar, Cat

Short description of the classes:

@Stateful public class Dog implements Animal {...}

@Stateful public class Cat implements Animal {...}

@BarBinding @Stateless
public class Bar {
    @EJB
    Animal animal;
}

@BarBinding @Priority(1000) @Interceptor
public class BarInterceptor {
    @EJB
    Animal animal;
}

Bar gets injected an instance of Cat, whereas BarInterceptor gets injected an instance of Dog, which IMHO contradicts (1).

Test case at: https://github.com/bafco/cdi-tck/tree/beanAccessibility
(org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.jndi.ejb.InterceptorEnvironmentEjbTest)