Most of the leaks are emanating from X, which is known to have memory leaks. There's nothing you can do about those. The others seem to be related to system calls; these might be actual leaks, or they might be an artifact of the kernel's internal memory management that don't actually leak memory. Like the X leaks, there's nothing you can do about them.

If you run your program for an extended period of time and exercise all of it's functionality over and over again, and the amount of memory leaked stays relatively constant, I'd quit worrying about it. You'll pay a small, fixed cost per application startup until someone gets around to fixing them, if they ever do.

If memory use grows continuously over time, it might be worth a more detailed look.