It’s my understanding that a function’s WASM must be run through wasm-opt, and by using the latest wasip1 target, wasm-opt is not run automatically.
The short term fix is to manually run compiled wasm through wasm-opt. Nick mentioned that this may be done automatically for you in a future CLI release.