Memory usage explodes when field contains many dates

Our team has found a potential memory leak or at least memory mismanagement in the component.
Our data is loaded through the Custom Data Source API. The field in question contains ~22,000 values which are dates corresponding to every day from 1970 to 2029. 
The /fields request advertises the field like so:

{
    "uniqueName": "Date",
    "type": "date"
},

The calls to /members returns 5 pages of up to 5,000 members each. As they load the memory usage starts to increase to about 2GB until the browser becomes sluggish and locks up with an error message (in the case of Chrome, see included screenshot).
What is telling is that if as a test we return type: "number" from the /fields call, then all the field's members are loaded and the memory usage barely changes.
We have been able to reproduce this on Chrome (103.0.5060.66) and Firefox (which tends to not actually lock up but manages to deal with the memory glut).