The AlwaysTenure and NeverTenure options were added in the 1.4.2
time frame and are essentially equivalent to setting MaxTenuringThreshold=0
and MaxTenuringThreshold=<max>. However, these flags are not consistently
applied across all garbage collectors. The relationship seems to be
reasonablely well implemented in Parallel Scavenge and somewhat
implemented in ParNew in 1.6.0 and later, but AlwaysTenure and
NeverTenure have no effect on the Serial collector.

This has been a minor issue in general, but with the introduction of
Biased Locking in 1.5.0_06, the setting for <max> is different on
different releases. This introduces release dependent ambiguity
on the proper setting of <max> for NeverTenure semantics. A stronger
relationship between NeverTenure and MaxTenuringThreshold=<max> would
eliminate the release dependent ambiguity. Making AlwaysTenure and
NeverTenure apply to all garbage collectors would further improve
the usability of these options.