Earlier quoted context omitted.
In order to port other languages (Haskell, Go, Python) to target WASM, we definitely need the possibility of writing a GC in WASM. But to build an efficient GC, we need multithreading and synchronization/memory barrier primitives.
You can already compile your language's runtime to wasm; this includes the GC. The downsides is that now you're adding all that to your binary size. "GC support" means being able to integrate with JS's GC, basically, so that your language's wasm runtime could use it instead of your own, saving bytes.
The GHC runtime (that is huge) isn't much larger than a web font. It is not much out the range of the JS libraries out there.