t_westling: that is a genuine bug which cripples user experience but I do also understand your reasons for doing it. I am fully aware that a single bad pattern could take jenkins down due to too many matches.
I think that the best way to implement it is to add a variable (system properly?) that limits the number of matches, and that defaults to 1 (current behaviour).
Once implemented I would gladly change the value to 10 which seem like a good compromise.
PS. Remember that these matches could be scattered in very distant places in the console log, so identifying them does help a lot.
When can this bug be addressed?