I love the solution you have come up with, but would suggest that it is moved to StandardTokenizer instead of StandardAnalyzer.
StandardTokenizer is the class with the actual problem. Fixing it there would mean that everyone that uses StandardTokenizer gets a default fix, not just StandardAnalyzer.
For instance, see
LUCENE-1373, where most of the contrib Analyzers still suffer the buggy behavior with no workaround available.
I think that moving your "defaulting logic" to the tokenizer would fix all these Analyzers in one fell swoop.
I would provide suggested patches, but I am just about to go on holidays for 3 weeks. Is there a planned release date for v2.3.3 or v2.4?