CachedBodyOutputMessage usage like this will cause memory leak ?

### Question

` CachedBodyOutputMessage outputMessage = ResponseUtils.newCachedBodyOutputMessage(exchange);

return serverRequest.bodyToMono(String.class)
.switchIfEmpty(Mono.defer(() -> Mono.just("")))
.flatMap(convert)
.flatMap(body -> {
BodyInserter bodyInserter = BodyInserters.fromValue(body);
return bodyInserter.insert(outputMessage, new BodyInserterContext());
}).then(Mono.defer(() -> {
ServerHttpRequestDecorator decorator = new RequestDecorator(exchange, outputMessage);
return Mono.just(exchange.mutate().request(decorator).build());
})).onErrorResume(throwable -> ResponseUtils.release(outputMessage, throwable));`

if the filter after this , e.g check some parameter ，call response.write ,the cache body can be release ?

Start by tracing the shown CachedBodyOutputMessage flow through ResponseUtils.newCachedBodyOutputMessage, ResponseUtils.release, and the later filter's response.write call. Determine whether the cached body is released on that path, and document the observed lifecycle or a reproducible failure case.

Written by the indexing model from the issue text.