Weld eagerly reading the 'cid' parameter breaks Servlet specification compliance

Weld reading the 'cid' parameter means that it is not possible to read request input via a stream or reader, and also makes it impossible to set the charset that is used by the form parser.

This violates the servlet spec, and is already causing lots of problems for users. I know there are workarounds however this is a clear violation of the servlet spec, so we need a solution.

IMHO the best solution would be to delay conversation scope activation until it is actually required, which should also give us some performance benefits as well.