jiraissues macro will append invalid attributes to file velocity name, resulting in the macro failing

Recently I upgraded to Confluence 2.3.3 and found a bunch of my pages using the jiraissues macro failed. I figured out that this was being caused by some of the jiraissues macros having |max=100} on the end. I guess max is not an allowed property. Perhaps a property check was added in 2.3 that was not there before. This results in the following error in the log:

2007-03-09 17:50:01,709 ERROR [http-80-Processor15] [confluence.util.velocity.VelocityUtils] getRenderedTemplate Error occurred rendering template: templates/extra/jira/jiraissues-max=150.vm
org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'templates/extra/jira/jiraissues-max=150.vm'
at org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:501)

Clearly the illegal property is being appended to the macro name for some reason resulting in a search for a non existent Velocity file.