Reusing Spark Label is much slower than re-using UITextField, UIFTextField, or Halo Label

Steps to reproduce:
1. Run performance file attached

Actual Results:
Creating 600 UITextFields: 392 ms
Re-using those UITextFields: 25 ms
Creating 600 UIFTETextFields: 568 ms
Re-using those UIFTETextFields: 229 ms
Creating 600 spark Label: 550 ms
Re-using those spark Labels: 316 ms
Creating 600 mx Labels: 883 ms
Re-using those mx Labels: 230 ms

I took these numbers on a Mac OS 10.5.8 while running a release version of FP 10.1.50

In all cases re-using the text component is a lot quicker than recreating it. For instance, re-using a Halo Label is 26% of the cost re-creating it. For all of them:

UITextField: 6%
UIFTETextField: 40%
Spark Label: 57%
Halo Label: 26%

Re-using a Spark Label shouldn't be as expensive as it is. At a minimum, it should be in line with UIFTETextField, around 40% of the cost of creating it.

Expected Results:
Re-using Spark Label's should be more performant. This has a serious impact on List scrolling if there are a good amount of item renderers.

Workaround (if any):