There is a whole memory allocation system used to combat fragmentation toward the OS level. Erlang also uses a multi-tiered approach, but note that a lot of things are easier because there is far less sharing going on and more things are isolated.
IIUC it's enormous amounts of copying since Erlang processes are "shared nothing" and have separately collected private heaps. To reduce copying BEAM has a separate shared heap using refcounting to share big blobs.