Hi Andy Guibert, thanks for reporting back!

I would be more willing to jump through hoops if OpenLiberty users could actually leverage JavaFX in their applications somehow

This seems like a legitimate requirement to me. E.g. a user might want to work with the JavaFX property types within their domain model, in order to benefit from listener support etc. Agreed it's not a common scenario, but I definitely can see usefulness of this beyond running this TCK.

In terms of classloader separation, I don't know OpenLiberty at all, but isn't there a way to add modules to the server itself? Like common libraries you'd like to share across all deployments? This used to be possible for all the common servers at least back in the day. It'd be nice to explore this route before we commit to excluding these tests (at least by default). I'd strongly prefer the TCK to be as extensive as possible.