Since it correlates with an increase in binary size I would assume that this is caused by more code being emitted to LLVM. This can have multiple causes, and I’d suggest that you take a closer look at what’s inside the binary. Since I did not see an increase in my application, I suspect that some part of the standard library that you use got heavier to compile.
On Linux you can use nm --size-sort -r executable_name to print all the symbol names and types (only type t is relevant here) sorted by size, in there you can look for patterns (e.g. new entries at the top of the list, or large sets of continuous entries of comptime-duplicated functions) and compare it with the size on 0.15.
This should give you a hint of where in the standard library the size increase came from, and you may fix the issue by trying to avoid that part.