Looks like regular EnumDeserializer is cachable, but it's factory-based alternative not.
I think this is not intentional but accidental; there does not seem to be particular reason to prevent it, and creation is pretty costly (I actually found it by profiling production systems).