I would be it is a very sane feature and consistent feature which means this test is not correct ...

Wrong assumption. The TCK test must always follow the spec.

not really cause if nothing prevents in the spec to fail at startup then the test should enable that as well.

The fact, that the example above should work prevents such validation. It could be an impl-specific feature which has to be disabled when running the TCK though.