Clarification on Vue 3 SSR handling of v-on

I’m having a hard time understanding if I’m running into a known limitation of SSR in Vue 3, or a bug. If I attempt to SSR compile a component containing component tags with event bindings, e.g.:

    <bc-selection-control
          :id="id + '-release-control'"
          v-model:selectedIndex="currentReleaseSlideIndex"
          class="bc-retail__release-control"
          :controlType="currentReleaseControlType"
          :options="releaseOffers"
          :optionsTransform="releaseOptionsTransform"
          :selectedDefault="selectDefaultRelease"
          @selectionchange="onReleaseSelectionChange"
          @selectionmount="onReleaseSelectionChange"
        />

Then on the other end I get something like:

serverRenderer.ssrRenderComponent(_component_bc_selection_control, {
    id: $setup.id + '-release-control',
    selectedIndex: $setup.currentReleaseSlideIndex,
    "onUpdate:selectedIndex": $event => ($setup.currentReleaseSlideIndex = $event),
    class: "bc-retail__release-control",
    controlType: $setup.currentReleaseControlType,
    options: $props.releaseOffers,
    optionsTransform: $setup.releaseOptionsTransform,
    selectedDefault: $setup.selectDefaultRelease
  }, null, _parent)

Note that the @selectionchange and @selectionmount bindings are stripped out. This is causing undesired side effects in my component, but I know there are certain things SSR-compiled components can’t do by design (like reactivity). It seems strange though, because onUpdate:selectedIndex is not stripped, even though all three are technically event bindings, which makes me wonder if this is a bug. Also, this comment from the source seems to indicate that component tags SHOULD have v-on bindings preserved? vue-next/ssrTransformComponent.ts at master · vuejs/vue-next · GitHub

I’d appreciate any help determining whether this is behaving as expected, or if I should go file a bug report.