CDI portable extensions with missing dependencies in fields fail to deploy

The following CDI extension fails to deploy if Foo is not on classpath:

public class BrokenExtension implements Extension {
    private Foo foo;
}

However, if the missing dependency is not a field but a parent class as in the following, the extension is disregarded by the container, but the archive deploys successfully:

public class BrokenExtension extends Foo implements Extension {
}

It would be more consistent if the behaviour from the second case applied in both cases.