Hello,
That seems to have worked! After disabling the console-level logging (but still having error-level logging enabled), we had another instance of this issue popping up. However, nothing is logged in our error log. Thus, we're assuming that this issue probably doesn't have anything to do with jsReport (possibly a locked file issue instead). We'll continue to monitor the issue but I get the feeling this may be being caused by stale filehandles, since we have also been getting EPERM errors as well related to this issue.
Thank you for your help!