The `Set` exposed via the lazy computation:

                    ResourceBundle info = getBreakIteratorInfo();
                    Set<String> k = info.keySet();
                    k.removeAll(NON_DATA_KEYS);

is using a mutable set. Also, the laziness could be better handled by Stable Values rather than a double-checked locking solution.