RSC: Passing element in loader causes missing key prop warning unless component uses default export — React Router v7.14.2

[semet]

Environment
React Router v7.14.2, Framework mode, RSC enabled

Description
When returning a JSX element from a loader and rendering it in a named export component, a key prop warning appears in the console. The warning disappears when the component is changed to a default export — with no other changes.

Steps to reproduce
Step 1. Return a JSX element from a loader:

export async function loader() {
  return {
    message: 'Message from the server!',
    element: <p>Element from the server!</p>,
  }
}

Step 2. Render it inside a named export component:

export function ServerComponent({ loaderData }: Route.ComponentProps) {
  return (
    <div className="container mx-auto rounded-2xl bg-slate-50 p-4">
      <h2 className="text-2xl font-bold">Server Component</h2>
      <span>{loaderData.message}</span>
      {loaderData.element}
    </div>
  )
}

Result: A key prop warning appears in the console.

Workaround
Changing the component to a default export makes the warning go away:

export default function Page({ loaderData }: Route.ComponentProps) {
  return (
    <div className="container mx-auto rounded-2xl bg-slate-50 p-4">
      <h2 className="text-2xl font-bold">Server Component</h2>
      <span>{loaderData.message}</span>
      {loaderData.element}
    </div>
  )
}

Alternatively, adding an explicit key prop to the element returned from the loader also suppresses the warning.

Question
Is this behavior intentional? Should JSX elements passed through a loader always require an explicit key, or is the named-export path not yet fully supported for RSC?