Is this really a BitLocker issue or more an issue inherent in the hardware design?
EDIT: Okay, looks like Microsoft could do better:
By kernel-level debugging with WinDbg, the researcher observed BitLocker operations during the Windows boot process, which revealed that while Microsoft attempts to erase encryption keys using functions like SymCryptSessionDestroy, some keys persist on the heap, potentially due to incomplete key destruction mechanisms.
But maybe the hardware/UEFI should immediately wipe memory upon restarting anyway..?
It doesn't already have to be running. BitLocker retrieves its keys from TPM by default, so just booting a device will place the keys in memory.