ID 576062 - Overwriting an existing EXR sequence leaves behind tmp files [Windows only]

Problem summary
Overwriting an existing EXR sequence leaves behind tmp files. This issue only appears to occur on Windows.
 
Customer reported version
Nuke 15.0v2
 
Customer reported platform
Windows 10
 
Steps to reproduce
 
1) Open Nuke.
 
2) Create a CheckerBoard and Write node. 
 
3) Render an EXR sequence.
 
4) Read this EXR sequence back into your existing script. 
 
5) Connect the Read node to the existing Write node and render the EXR sequence again.
 
Expected behaviour
The existing EXR frames should be overwritten, without leaving tmp files behind.
 
Actual behaviour
The EXR sequence is overwritten, however, there will be tmp files left in the render directory.
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke 15.0v4 - Windows 10
Nuke 12.0v1 - Windows 10
 
Unable to reproduce bug in:
Nuke 15.0v4 - macOS 12 (Monterey) - Linux Rocky 9
 
Earliest version tested
Nuke 12.0v1 - Windows 10
- This issue appears to be in all tested versions of the product on Windows