Totally agree with Tomas Remes first comment, spec states in 3.11

A bean type must be proxyable if an injection point resolves to a bean:

It implies that if there's no injection point, the bean type doesn't have to be proxyable.

Tests exist for non proxyable bean detected at deployment, you can check all of them in the version of the spec with assertion:

http://docs.jboss.org/cdi/spec/2.0/cdi-spec-with-assertions.html#unproxyable

UnproxyableManagedBeanTest relates to 6.5.4 where UnproxyableResolutionException is clearly stated:

http://docs.jboss.org/cdi/spec/2.0/cdi-spec-with-assertions.html#contextual_reference

So for me this test is consistent with the spec.